Additional Notes -- January 1995
Remoteboot Service for Windows NT(TM) Server version 3.51
--------------------------------------------------------
This document contains information about the Remoteboot service for
Microsoft(R) Windows NT Server version 3.51 that wasn't available
when the documentation was printed.

1.  Clarification on Logons
2.  Microsoft Windows 3.0 Not Supported (version 3.1 recommended)
3.  Running Microsoft Windows 3.1 on your Remoteboot Workstation
4.  Using RPLCMD to Create a Profile or Workstation Record
5.  Migrating from LAN Manager for OS/2 Remoteboot with Floppy Installation
6.  Migrating from Microsoft Windows NT 3.5 Remoteboot
6.5 Migrating from Microsoft Windows NT 3.5 Remoteboot with
        Floppy Installation
--------

1. Clarification on Logons
---------------------------
The first logon after starting a remoteboot workstation (remoteboot logon)
is logging on using the workstation's account, supplying the password
associated with this computer (regardless of who is using it).  After the
computer is running, you need to log on using your own username and password.


2. Microsoft Windows 3.0 Not Supported (version 3.1 recommended)
-----------------------------------------------------------------
Microsoft Windows 3.0 is not supported with the Remoteboot service for
Windows NT Server.  You should upgrade to Microsoft Windows 3.1.


3. Running Microsoft Windows 3.1 on your Remoteboot Workstation
----------------------------------------------------------------

If you run Microsoft Windows 3.1 on a remoteboot workstation, you must add
the following lines to the end of the [386enh] section in the SYSTEM.INI file:
   TimerCriticalSection=5000
   UniqueDosPSP=True
   PSPIncrement=2


4. Using RPLCMD to Create a Profile or Workstation Record
----------------------------------------------------------
When RPLCMD is used to create a profile or a workstation record,
the newly created profile or workstation files
on the server will not have proper permissions.  This can be
corrected by running "fix security" from Remoteboot Manager.  In
general, RPLCMD should be used only for those tasks that
are inaccessible via Remoteboot Manager.


5. Migrating from LAN Manager for OS/2 Remoteboot with Floppy Installation
---------------------------------------------------------------------------
In order to convert a LAN Manager for OS/2 Remoteboot directory using floppy
install, you must first generate a tree with the new LAN Manager client
software.  Before starting the main installation procedure, do the following:

A.  Install the Remoteboot service as if you were using a new remoteboot
    directory.  Follow steps 1-7 of that procedure.
B.  Move the RPL tree to another name, for example

    cd _systemroot_
    ren RPL RPL.NEW

C.  In Control Panel, choose the Network icon.
D.  In the Network Settings dialog box, go to the Installed Network Software
    listbox and select the Remoteboot Service.
E.  Press the Remove button to uninstall the Remoteboot Service.
F.  Reboot your server.  You must reboot before trying to re-install the
    Remoteboot Service.

At this point, you have the new LAN Manager client software in
\_systemroot_\RPL.NEW.  You can now follow the regular procedure for
converting a LAN Manager for OS/2 remoteboot directory.  In step 11,
instead of specifying d:\clients\rpl\_subdir_ as the location of the
LAN Manager client software, specify \_systemroot_\RPL.NEW\_subdir_.
Be sure not to copy the files in the root directory of RPL.NEW,
in particular \_systemroot_\RPL.NEW\rplsvc.mdb and system.mdb.


6. Migrating from Microsoft Windows NT 3.5 Remoteboot
-----------------------------------------------------
There are several remoteboot improvements introduced in Microsoft Windows NT
version 3.51:
  (1) New NETWKSTA.* files to improve client behavior when the server is
        running the NTFS file system;
  (2) Support for two additional network adapter types:
        Intel EtherExpress PRO, and
        Madge Smart 16/4 Ringnode (token-ring); and
  (3) Support for 3Com ELNK II cards with new vendor ID 0020AF; and
  (4) Support for 3Com 3Stations with new vendor ID 000062.
If you install a fresh copy of the remoteboot service, you will already
have these improvements.  If you carry over your remoteboot database and
client files from version 3.5, you can add these improvements by using
the RPLUPD.BAT script, in the CLIENTS\RPL\UPDATE subdirectory of your
CD tree.  This will not interfere with your existing profiles and
workstations.  Make sure you have a backup copy of your RPL database files
before running RPLUPD.BAT.


6.5 Migrating from Microsoft Windows NT 3.5 Remoteboot with
        Floppy Installation
-----------------------------------------------------------
If you carry over your remoteboot database and client files from version 3.5,
and you wish to add support for the adapters, you will need to follow this
procedure if you use floppy installation:

A.  Install the Remoteboot service as if you were using a new remoteboot
    directory.  Follow steps 1-7 of that procedure.
B.  Move the RPL tree to another name, for example

    cd _systemroot_
    ren RPL RPL.NEW

C.  Copy your old RPL tree in the place of the active tree, for example

    xcopy /E D:\OLDNT\RPL _systemroot_\RPL

D.  Use RPLUPD to update the active tree, for example

    net start remoteboot
    cd _systemroot_\RPL.NEW\UPDATE
    RPLUPD _systemroot_\RPL.NEW _systemroot_\RPL
